@fkorotkov is there a way to have a VM run ephemerally in that it will restore from the saved state but not save the state at the end. Then the next time the VM runs it will restore from the same/original saved state

@Jon889 you can clone a VM into a temporary one which is very fast and will clone the state. Then you can run this temporary VM and delete it once not needed anymore.

@fkorotkov Ah I thought that would invalidate the snapshot, as then multiple machines could be run. Also is it not possible to use snapshots with mounted directories? I get Failed to suspend the VM: Invalid virtual machine configuration. Unsupported directory sharing device in configuration. in which case it seems like tart shouldn't allow --suspendable and --dir to be used together

Sees you can resume a suspended VM with a mounted directory though. So you can run a suspendable VM without a mount, configure it and suspend. Then resume it again but this time with a mounted directory. The only part that is failing is the actual suspending of a VM with a mounted directory.

Adding the validation in #623

@fkorotkov Do you think there is any way around not being able to use suspendible VMs with mounted directories? macOS should have the ability to do it as USB drives can be plugged in and out without any notice.

@fkorotkov Do you think there is any way around not being able to use suspendible VMs with mounted directories? macOS should have the ability to do it as USB drives can be plugged in and out without any notice.

Unfortunately Virtualization.Framework does not support mounting USB drives yet, see #139 and utmapp/UTM#3778 for more details.

Mounting a block device could be an option, but a quick test shows that it also works incorrectly because the guest seems to be overwriting the host's device state/file table on resume from snapshot.